Sourced from @​sentry/react's releases.

7.58.1

• fix(node): Set propagation context even when tracingOptions are not defined (#8517)

Bundle size 📦

Path	Size
@​sentry/browser - ES5 CDN Bundle (gzipped + minified)	21.95 KB
@​sentry/browser - ES5 CDN Bundle (minified)	69.13 KB
@​sentry/browser - ES6 CDN Bundle (gzipped + minified)	20.28 KB
@​sentry/browser - ES6 CDN Bundle (minified)	60.38 KB
@​sentry/browser - Webpack (gzipped + minified)	21.9 KB
@​sentry/browser - Webpack (minified)	71.51 KB
@​sentry/react - Webpack (gzipped + minified)	21.92 KB
@​sentry/nextjs Client - Webpack (gzipped + minified)	50.58 KB
@​sentry/browser + @​sentry/tracing - ES5 CDN Bundle (gzipped + minified)	30.11 KB
@​sentry/browser + @​sentry/tracing - ES6 CDN Bundle (gzipped + minified)	28.16 KB
@​sentry/replay ES6 CDN Bundle (gzipped + minified)	49.42 KB
@​sentry/replay - Webpack (gzipped + minified)	43.1 KB
@​sentry/browser + @​sentry/tracing + @​sentry/replay - ES6 CDN Bundle (gzipped + minified)	69.51 KB
@​sentry/browser + @​sentry/replay - ES6 CDN Bundle (gzipped + minified)	61.82 KB

7.58.0

Important Changes

• Performance Monitoring not required for Distributed Tracing

This release adds support for distributed tracing without requiring performance monitoring to be active on the JavaScript SDKs (browser and node). This means even if there is no sampled transaction/span, the SDK will still propagate traces to downstream services. Distributed Tracing can be configured with the tracePropagationTargets option, which controls what requests to attach the sentry-trace and baggage HTTP headers to (which is what propagates tracing information).

Sentry.init({
  tracePropagationTargets: ["third-party-site.com", /^https:\/\/yourserver\.io\/api/],
});

• feat(tracing): Add tracing without performance to browser and client Sveltekit (#8458)

• feat(node): Add tracing without performance to Node http integration (#8450)

• feat(node): Add tracing without performance to Node Undici (#8449)

• feat(node): Populate propagation context using env variables (#8422)

• feat(core): Support AggregateErrors in LinkedErrors integration (#8463)

This release adds support for AggregateErrors. AggregateErrors are considered as Exception Groups by Sentry, and will be visualized and grouped differently. See the Exception Groups Changelog Post for more details.

Exception Group support requires Self-Hosted Sentry version 23.5.1 or newer.

• feat(replay): Add a new option networkDetailDenyUrls (#8439)

This release adds a new option networkDetailDenyUrls to the Replay integration. This option allows you to specify a list of URLs that should not be captured by the Replay integration, which can be used alongside the existing networkDetailAllowUrls for finely grained control of which URLs should have network details captured.

... (truncated)

Sourced from @​sentry/react's changelog.

7.58.1

• fix(node): Set propagation context even when tracingOptions are not defined (#8517)

7.58.0

Important Changes

• Performance Monitoring not required for Distributed Tracing

This release adds support for distributed tracing without requiring performance monitoring to be active on the JavaScript SDKs (browser and node). This means even if there is no sampled transaction/span, the SDK will still propagate traces to downstream services. Distributed Tracing can be configured with the tracePropagationTargets option, which controls what requests to attach the sentry-trace and baggage HTTP headers to (which is what propagates tracing information).

Sentry.init({
  tracePropagationTargets: ["third-party-site.com", /^https:\/\/yourserver\.io\/api/],
});

• feat(tracing): Add tracing without performance to browser and client Sveltekit (#8458)

• feat(node): Add tracing without performance to Node http integration (#8450)

• feat(node): Add tracing without performance to Node Undici (#8449)

• feat(node): Populate propagation context using env variables (#8422)

• feat(core): Support AggregateErrors in LinkedErrors integration (#8463)

This release adds support for AggregateErrors. AggregateErrors are considered as Exception Groups by Sentry, and will be visualized and grouped differently. See the Exception Groups Changelog Post for more details.

Exception Group support requires Self-Hosted Sentry version 23.5.1 or newer.

• feat(replay): Add a new option networkDetailDenyUrls (#8439)

This release adds a new option networkDetailDenyUrls to the Replay integration. This option allows you to specify a list of URLs that should not be captured by the Replay integration, which can be used alongside the existing networkDetailAllowUrls for finely grained control of which URLs should have network details captured.

Sentry.init({
  integrations: [
    new Sentry.Integrations.Replay({
      networkDetailDenyUrls: [/^http:\/\/example.com\/test$/],
    }),
  ],
});

Other Changes

• feat(core): Add helpers to get module metadata from injected code (#8438)
• feat(core): Add sampling decision to trace envelope header (#8483)
• feat(node): Add trace context to checkin (#8503)
• feat(node): Export getModule for Electron SDK (#8488)
• feat(types): Allow user.id to be a number (#8330)

... (truncated)

• 03d3e87 release: 7.58.1
• cb799d4 Merge pull request #8524 from getsentry/prepare-release/7.58.1
• e8113fe meta(changelog): Update changelog for 7.58.1
• 0f2d390 Merge pull request #8519 from getsentry/hubertdeng123/remove-stale
• a05c225 chore(tracing-internal): Fix eslint warning (#8516)
• f0862a1 chore(core): Remove eslint warnings (#8515)
• 5f7a0fb fix(node): Set propagation context even when tracingOptions are not defined (...
• 6be123e test(replay): skip captures multiple multi clicks on firefox and webkit (#8...
• 0931ab2 delete stale.yml
• 3d592c0 Merge pull request #8518 from getsentry/master
• Additional commits viewable in compare view

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)